feat: SLS-494 run users' worker initialization code - #567

runpod/serverless/modules/rp_job.py:347

• run_job_generator bounds the handler/traceback string via clip(...), but then appends up to 16KB of captured logs afterward, which can defeat the intended bounding and inflate the streamed error payload. Consider clipping the final assembled error string instead.

            error = clip(f"handler: {str(err)} \ntraceback: {traceback.format_exc()}")
            if captured_logs:
                error += f"\nlogs:\n{captured_logs}"
            yield {"error": error}

runpod/serverless/modules/rp_initializer.py:96

• Docstring typo: “abandoned an die” should be “abandoned and die”.

    """Run a blocking callable on a daemon thread instead of `asyncio.to_thread` so if stuck,
    it can be abandoned an die without blocking the executor shutdown and process exit."""

runpod/serverless/modules/rp_initializer.py:140

• run_initializer_async treats timeout=0 as “no timeout” because it uses a truthiness check (if timeout:). If a user sets init_timeout: 0 expecting an immediate timeout, it will instead run unbounded.

        if timeout:
            await asyncio.wait_for(asyncio.ensure_future(awaitable), timeout=timeout)
        else:
            await awaitable

runpod/serverless/init.py:150

• The docstring says the initializer runs “before the job loop begins”, but the implementation can still acquire jobs while the initializer runs (the gate only prevents the handler from executing). This wording is misleading for SDK users.

    config["initializer"] (Callable, optional): Startup work before the job loop begins,
        e.g. loading a model or starting an inference engine.